home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
1995.02
/
000072_Robin.Fairbairns@cl.cam.ac.uk_Thu Feb 9 17:31:20 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-02-28
|
1KB
Received: from swan.cl.cam.ac.uk by cs.umb.edu with SMTP id AA27813
(5.65c/IDA-1.4.4 for <tex-k@cs.umb.edu>); Sat, 11 Feb 1995 06:30:19 -0500
Received: from dorceus.cl.cam.ac.uk (user rf (rfc931)) by swan.cl.cam.ac.uk
with SMTP (PP-6.5) to cl; Thu, 9 Feb 1995 17:31:37 +0000
To: Frank Jensen <fj@iesd.auc.dk>
Cc: Denis.Roegel@loria.fr, tex-k@cs.umb.edu
Subject: Re: about MakeTeXPK
In-Reply-To: Your message of "Thu, 09 Feb 1995 16:29:35 +0100." <199502091529.QAA00095@verdande.iesd.auc.dk>
Date: Thu, 09 Feb 1995 17:31:20 +0000
From: Robin Fairbairns <Robin.Fairbairns@cl.cam.ac.uk>
Message-Id: <"swan.cl.cam.:141980:950209173149"@cl.cam.ac.uk>
Frank Jensen writes (quoting Denis):
> > How can I use MakeTeXPK both with xdvik and dvipsk,
> > but call gsftopk in the first place when a PS fonts
> > has to be displayed and outputing an error in
> > the second place with dvips. [...]
>
> Why is this interesting? Dvips would (should) never call MakeTeXPK
> for a PS font, while it is OK for xdvi to do that.
Indeed, xdvi will cause gsftopk to run in precisely those situations
when dvips would have used a resident font. ... at least, that's how
I understand its behaviour (we don't have that behaviour set up here,
so my beliefs rest on potentially imperfect understanding of code I've
read).
Robin